allow to reload web_app immediately via param for definition #442
Conversation
* Sometimes it's needed to immediately relaod a web_app/apache2 to continue the chef-run, since the webserver is lateron used. This patch allows to set the reload_speed for the web_app definition (apache2 service) via the parameter :reload_speed. The default behaviour does not change.
| @@ -557,6 +557,8 @@ combine the template with enabling a site, see `web_app`. | |||
|
|
|||
| * `name` - Name of the site. | |||
| * `enable` - Default true, which uses `a2ensite` to enable the site. If false, the site will be disabled with `a2dissite`. | |||
| * `reload_speed` - Defaults to `:delayed` and can be set to `:immediately` to | |||
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
|
I totally agree with @punkle here, but i think the biggest issue is the fact that these are definitions. @svanzoest Are there any plans on refactoring these to resources? I would be happy to help with that. |
|
@jklare this is part of #414 and the apache2@customresources branch has the current implementation. I am looking for feedback and some testing on that branch. I'd love to get your perspective on #414 |
|
@svanzoest sounds great, i will look trough the changes in that branch and post my feedback in #414 (sry for responding so slowly, i was on holiday the last 2 weeks) |
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
continue the chef-run, since the webserver is lateron used. This patch
allows to set the reload_speed for the web_app definition (apache2
service) via the parameter :reload_speed. The default behaviour does not
change.